Copyright: Copyright (c) MicroGate Corporation 1998


 Network Settings

The network settings page configures the network protocols used by the SyncLink adapter.

IP Enabled

Select this check box to enable the Internet Protocol (IP) over the PPP connection. IP is the protocol used for internet communications. If this option is not selected, the IP protocol is not negotiated and no IP traffic is transferred over the PPP connection.

Remote IP Address

This is an optional parameter. If the remote peer requires dynamic assignment of it’s IP address then enter the IP address of the remote peer in this field. When a connection is made, the SyncLink software assigns this IP address to the remote peer.

IPX Enabled

Select this check box to enable the Internetworking Packet Exchange (IPX) protocol over the PPP connection. IPX is used in Novell networking environments. If this option is not selected, the IPX protocol is not negotiated and no IPX traffic is transferred over the PPP connection.

Local IPX Node Address

The IPX node address uniquely identifies an IPX interface on a network segment. This address is set automatically during adapter installation. In some rare instances it may be necessary to alter this address to prevent a conflict with the remote IPX node address. The IPX node address is also used as the Ethernet MAC address for the SyncLink adapter LAN emulation.

Enable interface at startup

Select this check box to enable the SyncLink interface when the computer starts up. While the interface is enabled, the SyncLink adapter continuously attempts and maintains the PPP connection. If this option is not selected, then the MGWAN.EXE control program must be used to enable and disable the interface.

NOTE:

When IP is enabled, you MUST manually set the IP address for this network adapter. Do NOT select DHCP for dynamic IP address assignment.

NOTE:

When IPX is enabled, you MUST manually set the IPX network number and packet type for this adapter in the IPX network settings.


 Security Settings

The Security page specifies which authentication protocols are used and the associated user names and passwords. Authentication verifies the identity of each peer when establishing a PPP connection. The authenticator is defined as the end of the link requiring authentication. Each end of the link independently requires authentication so both ends may require authentication, only one end or the other may require authentication, or neither end may require authentication.

The SyncLink adapter supports two standard authentication protocols used with PPP:

PAP Password Authentication Protocol (RFC1334)

A clear text user name and password are sent to the authenticator. If the user name and password are correct the authenticator responds with a positive acknowledgement and continues with link negotiation. If the user name or password is incorrect, the authenticator responds with a negative acknowledgement and either terminates the connection or waits for another user name and password attempt.

CHAP Challenge Handshake Authentication Protocol (RFC1994)

The authenticator sends a challenge to the remote peer. The peer responds with an encrypted response based on the challenge and the password. The authenticator verifies the response and sends a positive or negative acknowledgement to the peer. This protocol is superior to PAP in that the password itself is never sent across the link.

NOTE:

Microsoft uses a proprietary and incompatible version of CHAP called MS-CHAP. Microsoft RAS and RRAS do not support CHAP as an authenticator but do support being authenticated by a remote peer with CHAP. When connecting to RAS/RRAS operating as an authenticator, use the PAP protocol. This is done by selecting ‘Accept any authentication including clear text’ in the RAS/RRAS server network setup.

Local (Incoming) Authentication

The local computer is the authenticator requiring authentication from the remote peer.

Authentication Protocol

This pull down list selects the protocol used by the local computer to authenticate the remote peer. The local computer is the authenticator. If the remote peer does not recognize or support the selected protocol, or sends the wrong credentials then the SyncLink adapter terminates the connection. If no authentication is required then select ‘None’.

User Name

The user or host name required by the authenticator.

Password

The password or secret required by the authenticator for the specified user name.

Remote (Outgoing) Authentication

The remote peer is the authenticator requiring authentication from the local computer.

Authentication Protocol

This pull down list selects the protocol used by the remote peer to authenticate the local computer. The remote peer is the authenticator. If the remote peer does not request authentication then these settings have no effect. If the remote peer requires authentication but refuses to negotiate the selected protocol then the SyncLink adapter terminates the connection. If the remote peer does not accept the local credentials then the SyncLink adapter terminates the connection. If no authentication is required then select ‘None’.

User Name

The user or host name required by the authenticator.

Password

The password or secret required by the authenticator for the specified user name.


 Configuring the Serial Interface

The SyncLink adapter is shipped with one of its three serial interfaces pre-configured.  The serial interface is configured by placing the 17-position jumper on one of three jumper blocks (J5, J6, J7).  The jumper is placed so as to completely cover one of the jumper blocks.  If necessary, the serial interface can be changed by moving the jumper to the desired block.

To configure the serial interface of the SyncLink adapter, follow the steps outlined below.

1.	For convenience of jumper removal, a combination of two black 8-pin jumpers separated by a single-pin colored jumper is used to form the 17-position interface jumper.

NOTE:  The 8-pin jumpers are installed with the shorting bars visible on top.  This orientation MUST be maintained when relocating.

2.	Removal of the interface jumper is accomplished by first removing the colored jumper, then the black 8-pin jumpers one at a time using common pliers.

NOTE:  DO NOT  attempt removal with a screwdriver, needle-nose pliers, or any tool other than pliers.  This may cause damage to the jumper, the jumper block pins, or the board.

3.	Holding the SyncLink in one hand with the component side up, grasp the 8-pin jumper firmly about the middle with the pliers and gently remove it by applying sufficient perpendicular force away from the board.  The jumper should come off easily.

4.	Insert the jumpers by hand onto the corresponding pins of the desired interface jumper block with the shorting bars on top and push down firmly.

Electrical Interface

RS-232 Interface

Jumper J5 (ISA) or J1 (PCI) selects the RS-232 serial standard. This uses V.28 single-ended drivers and receivers for all signals and a DB-25 connector. This setting is used for connecting to slow speed serial devices such as modems.

V.35 Interface

Jumper J6 (ISA) or J2 (PCI) selects the V.35 serial standard. This uses V.11 differential drivers and receivers for data and clock signals. V.28 single ended drivers and receivers are used for the remainder of the serial signals. The SyncLink V.35 pinout may be used for direct connection to a DCE that implements the Codex V.35 pinout for a DB-25 connector. For DCE devices that use the ISO-2593 34-pin Block Connector, an adapter cable is required (available from MicroGate Corporation).

RS-422 Interface

Jumper J7 (ISA) or J3 (PCI) selects the RS-422 serial standard. This uses V.11 differential drivers and receivers for all serial signals. This standard is capable of data rates up to 10 Mbps. The SyncLink adapter supports the RS-530 standard for serial connector pinout through a DB-25 interface (no adapter cable required). RS-449 uses the same electrical specification as RS-530, but uses a DB-37 connector, so an adapter cable is required (available from MicroGate Corporation).

Data Port Signals (DB-25 Pin Serial Connector)

Tables 1, 2, and 3 give signal names and pinouts for the data port's RS-232, V.35, and RS-422 serial interfaces, respectively.

Table 1: RS-232 Data Port Pin Connections

Signal Name	Electrical Desc	DB-25 Pin No.
Earth Ground		1
Signal Ground		7
RTS	RS-232/V.28	4
CTS	RS-232/V.28	5
DTR	RS-232/V.28	20
DSR	RS-232/V.28	6
DCD	RS-232/V.28	8
RI (Ring)	RS-232/V.28	22
TxD	RS-232/V.28	2
RxD	RS-232/V.28	3
TxCLK	RS-232/V.28	15
RxCLK	RS-232/V.28	17
AuxCLK	RS-232/V.28	24

NOTES:

<Signal Name>+ represents the inverting input/output

<Signal Name>- represents the non-inverting input/output

Table 2: V.35 Data Port Pin Connections

Signal Name	Electrical Desc	DB-25 Pin No.	V.35 Block Pin No.
Earth Ground		1	A
Signal Ground		7	B
RTS	RS-232/V.28	4	C
CTS	RS-232/V.28	5	D
DTR	RS-232/V.28	20	H
DSR	RS-232/V.28	6	E
DCD	RS-232/V.28	8	F
RI (Ring)	RS-232/V.28	22	---
TxD+	RS-422/V.11	2	P
TxD-	RS-422/V.11	14	S
RxD+	RS-422/V.11	3	R
RxD-	RS-424/V.11	16	T
TxCLK+	RS-422/V.11	15	Y
TxCLK-	RS-422/V.11	13	AA
RxCLK+	RS-422/V.11	17	V
RxCLK-	RS-422/V.11	19	X
AuxCLK+	RS-422/V.11	24	U
AuxCLK-	RS-422/V.11	23	W

NOTES:

<Signal Name>+ represents the inverting input/output

<Signal Name>- represents the non-inverting input/output

Table 3: RS-422 Data Port Pin Connections

Signal Name	Electrical Desc	DB-25 (RS-530) Pin No.	DB-37(RS-449) Pin No.
Earth Ground		1	1
Signal Ground		7	19
RTS+	RS-422/V.11	4	7
RTS-	RS-422/V.11	19	25
CTS+	RS-422/V.11	5	9
CTS-	RS-422/V.11	13	27
DTR+	RS-422/V.11	20	12
DTR-	RS-422/V.11	23	30
DSR+	RS-422/V.11	6	11
DSR-	RS-422/V.11	22	29
DCD+	RS-422/V.11	8	13
DCD-	RS-422/V.11	10	31
TxD+	RS-422/V.11	2	4
TxD-	RS-422/V.11	14	22
RxD+	RS-422/V.11	3	6
RxD-	RS-424/V.11	16	24
TxCLK+	RS-422/V.11	15	5
TxCLK-	RS-422/V.11	12	23
RxCLK+	RS-422/V.11	17	8
RxCLK-	RS-422/V.11	9	26
AuxCLK+	RS-422/V.11	24	17
AuxCLK-	RS-422/V.11	11	35

NOTES:

<Signal Name>+ represents the inverting input/output

<Signal Name>- represents the non-inverting input/output


Diagnostics

The SyncLink adapter software tests the adapter each time the computer is started. If an error occurs, an event is posted to the event log with a source name of MGWAN.The system log can be viewed using the Event Viewer application. Start the Event Viewer application by selecting Programs -> Administrative Tools -> Event Viewer from the start menu. The same message is also displayed on the Diagnostics page of the SyncLink adapter properties.

The Diagnostics property page provides a data loopback test. This test sends and receives test frames to verify the correct operation of the device. The data is looped back internally if the Internal loopback mode radio button is selected. The data is looped back externally if the External radio button is selected. The external test requires a device connected to the adapter serial interface to loop the transmit data pin back to the receive data pin. A loopback connector is supplied with the adapter for this purpose. The internal test verifies the correct operation of the serial controller. The external test also verifies the correct operation of the adapter serial port.

To start the test, click the Start Test button.

The test will continue until the Stop Test button is clicked.

The results of the test are displayed in the Diagnostics property page.

WARNING: The data loopback test disrupts normal communications. Normal operation is resumed after the test has completed.


Hardware Settings

The hardware settings page configures how the software uses the hardware. For information on configuring the hardware itself, click on Configuring the Serial Interface and Adapter Switch and Jumper Settings.

Data Rate

The data rate is the speed in bits per second (bps) in which data is transferred between the SyncLink adapter and the communications device (CSU/DSU, Modem, etc.).

Example data rates:

V.34 Modem	28800bps

Leased DDS I CSU/DSU	56000bps

Bonded ISDN (2 B-Channels)	128000bps

T-1 CSU/DSU	1544000bps

Incorrectly setting this parameter could result in incorrect network timeouts.

Generate Clock

Data clocks are usually provided by the modem or CSU/DSU. In rare instances, it may be necessary for the adapter to generate these clocks. Enable this check box if the adapter needs to generate the data clocks. The clock signal is output on the AUXCLK serial signal. Depending on the application, external cabling may be necessary to route the AUXCLK signals to the correct RCLK and TCLK signals.

Serial Encoding

The SyncLink adapter supports NRZ and NRZI serial encoding. This setting must match that of the remote peer. PPP communications usually uses NRZ (default).

Restart Device

Clicking this button restarts the SyncLink WAN device. If you change any protocol options, such as the IP address or IPX network number, you must restart the device for the changes to be recognized. Changing any of the device parameters (Hardware, Network, or Security) automatically restarts the device when you click the OK button.


NULL Modem

A Synchronous NULL Modem is a device which connects two serial ports directly to each other, without using a modem or CSU/DSU.

Data Clocks

A NULL modem for synchronous communication is different from a NULL modem used for asynchronous communication. Synchronous communication uses clock signals, which MUST be supplied to both adapters. Usually the attached communications device (modem or CSU/DSU) provides the data clocks. When using a NULL modem, one of the adapters must be set to provide external clocks. The SyncLink adapter can provide a clock source on the AUX Clock pin of the serial interface. This is controlled in the Adapter Settings property page of the SyncLink SDLC Link Service setup. The NULL modem routes this clock output to the transmit and receive clock inputs on both adapters. This means the NULL modem must be attached with the Clock Source end to the SyncLink adapter that is supplying the external clock signal.

NULL Modem Wiring

The exact wiring of the NULL modem will depend on the serial interface configuration of the SyncLink adapter: RS-232, V.35, or RS-530.

The following NULL modem cabling requirements are necessary for use with the SyncLink adapter:

RS-232 Null Modem

Clock Source End

DSR (Pin 6)	DTR (Pin 20)

DCD (Pin 8)	RTS, CTS (Pins 4,5)

DTR (Pin 20)	DSR (Pin 6)

RTS, CTS (Pins 4,5)	DCD (Pin 8)

Tx Clock, RxClock, AUX Clock 	TxClock,Rx Clock

(Pins 15,17,24)	(Pin 15,17)

Transmit Data[TxD] (Pin 2)	Receive Data[RxD] (Pin 3)

Receive Data[RxD] (Pin 3)	Transmit Data[TxD] (Pin 2)

V.35 Null Modem

The V.35 NULL modem is similar to the RS-232 NULL modem, except the data and clock signals use two wires each. In this table, each signal pair is described by <Signal Name>+ and <SignalName>-.

Clock Source End

DSR (Pin 6)	DTR (Pin 20)

DCD (Pin 8)	RTS, CTS (Pins 4,5)

DTR (Pin 20)	DSR (Pin 6)

RTS, CTS (Pins 4,5)	DCD (Pin 8)

Tx Clock+, RxClock+, AUX Clock+	TxClock+, Rx Clock+

(Pins 15,17,24) 	(Pins 15,17)

Tx Clock-, RxClock-, AUX Clock- 	TxClock-, Rx Clock-

(Pins 13,19,23)	(Pin 13,19)

Transmit Data[TxD+] (Pin 2)	Receive Data[RxD+] (Pin 3)

Transmit Data[TxD-] (Pin 14)	Receive Data[RxD-] (Pin 16)

Receive Data[RxD+] (Pin 3)	Transmit Data[TxD+] (Pin 2)

Receive Data[RxD-] (Pin 16)	Transmit Data[TxD-] (Pin 14)

RS-530 Null Modem

The RS-530 NULL modem uses two wires per serial signal. In this table, each signal pair is described by <Signal Name>+ and <SignalName>-.

Clock Source End

DSR+ (Pin 6)	DTR+ (Pin 20)

DSR- (Pin 22)	DTR- (Pin 23)

DCD+ (Pin 8)	RTS+,CTS+ (Pins 4,5)

DCD- (Pin 10)	RTS-,CTS- (Pins 19,13)

DTR+ (Pin 20)	DSR+ (Pin 6)

DTR- (Pin 23)	DSR- (Pin 22)

RTS+,CTS+ (Pins 4,5)	DCD+ (Pin 8)

RTS-,CTS- (Pins 19,13)	DCD- (Pin 10)

Tx Clock+, RxClock+, AUX Clock+ 	TxClock+,Rx Clock+

(Pins 15,17,24)	(Pins 15,17)

Tx Clock-, RxClock-, AUX Clock- 	TxClock-,Rx Clock-

(Pins 12,9,11)	(Pins 12,9)

Transmit Data[TxD+] (Pin 2)	Receive Data[RxD+] (Pin 3)

Transmit Data[TxD-] (Pin 14)	Receive Data[RxD-] (Pin 16)

Receive Data[RxD+] (Pin 3)	Transmit Data[TxD+] (Pin 2)

Receive Data[RxD-] (Pin 16)	Transmit Data[TxD-] (Pin 14)


Adapter Switch and Jumper Settings

The SyncLink PCI adapter has no jumper or switch settings for configuring the resources used by the adapter. Adapter resources are automatically configured by the computer BIOS and the operating system. The adapter uses two I/O address ranges, two memory address ranges, and an interrupt.

WARNING

Computers with both ISA/EISA and PCI buses may reserve interrupt levels for either the ISA or PCI buses. This is often configured in the CMOS setup that is available when the computer is turned on. Be sure a free interrupt level is available to the PCI bus for use by the SyncLink adapter. Consult your computer documentation for details about CMOS setup procedures.

The SyncLink ISA adapter has three resources that must be configured by properly setting the DIP switches and jumpers on the adapter.

DIP Switch S1

The DIP switch is located in the lower center of the adapter. The switch has 3 positions which determine which base I/O address the adapter uses:

Base I/O Address	Sw1 Pos1	Sw1 Pos 2	Sw1 Pos 3
100	OFF	OFF	OFF
110	OFF	OFF	ON
120	OFF	ON	OFF
200	OFF	ON	ON
210	ON	OFF	OFF
300	ON	OFF	ON
310	ON	ON	OFF
Disabled	ON	ON	ON

The SyncLink interrupt is set using the Jumper marked USC IRQ located at the bottom center of the adapter. The jumper block is a set of pins arranged 2 pins by 8 pins. To select a particular IRQ level look at the label above the jumper block. Place the jumper on the pair of pins below the desired IRQ level such that the jumper is vertically oriented as shown below:

Interrupt jumper setting for IRQ level 5.

The DMA Channel is set in a similar fashion as the IRQ level. The jumper blocks for the DMA settings are located in the lower left area of the adapter. Two jumpers must be positioned for the DMA Channel: DMA Request and DMA Acknowledge. Look at the label above the jumper blocks for the desired DMA channel. Place BOTH jumpers on the REQ and ACK block for the same DMA channel as shown below:

DMA Jumper settings for DMA Channel 3.


Warranty

This section describes the limited hardware warranty.

Limited Hardware Warranty

MicroGate Corporation warrants this hardware product to be in good working order for a period of one (1) year from the date of purchase by Buyer from MicroGate Corporation or an authorized MicroGate Corporation Reseller. Should the product fail to be in good working order at any time during this one year warranty period, MicroGate Corporation will, at its option, repair or replace this product at no additional charge except as set forth below. Repair parts or replacement products will be furnished on an exchange basis and will be either reconditioned or new at the discretion of MicroGate Corporation. Repaired or replacement units shall be warranted for the remainder of the original one year warranty period. This limited warranty does not include service to repair damage to the product resulting from accident, disaster, misuse, abuse, or modifications which have not been made or authorized by MicroGate Corporation.

To validate this Limited Hardware Warranty, Buyer must complete and return the Limited Hardware Warranty Registration Form supplied by MicroGate Corporation within thirty (30) days of purchase.

Beyond the warranty period, MicroGate Corporation will repair or replace defective hardware products for a fixed price if defects are not due to accident, disaster, abuse, misuse, or modifications which have not been made or authorized by MicroGate Corporation.

If this product should require service, obtain a Return Material Authorization (RMA) number from MicroGate Corporation and return the product in its original shipping carton (or equivalent shipping container with the board protected by one inch non-static padding) to the address below, shipping prepaid, along with proof of purchase, a return address, a telephone contact, and an explanation of the suspected defect. You agree to insure the product or assume the risk of loss or damage in transit. C.O.D returns are not accepted.

MicroGate Corporation

9501 N. Capital of Texas Highway, Suite 105

Austin, Texas 78759

Attention: RMA #:________

There are no warranties, expressed or implied, including, but not limited to, those of merchantability and fitness for a particular purpose, which extend beyond the description and duration set forth herein.

MICROGATE CORPORATION'S SOLE OBLIGATION UNDER THIS WARRANTY IS LIMITED TO THE REPAIR OR REPLACEMENT OF A DEFECTIVE PRODUCT AND MICROGATE CORPORATION SHALL NOT, IN ANY EVENT, BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND RESULTING FROM THE USE OR POSSESSION OF THIS PRODUCT.

THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM STATE TO STATE.

Limited Hardware Warranty Registration

|	Please complete and mail this form to validate your MicroGate Corporation Limited Hardware Warranty.

|

Mail to:	MicroGate Corporation

|	9501 N. Capital of Texas Highway

Suite 105

|	Austin, Texas 78759

Attn: Warranty Registration

|

Date:___________________

|

|	Name:______________________________________________________

|

Phone: ____________________________________________________

|

|	Title: ____________________________________________________

|

Organization: _____________________________________________

|

|	Street Address: ___________________________________________

|	___________________________________________________________

|

City/State/Zip: ___________________________________________

|

|	Product Purchased: ________________________________________

|

Hardware S/Ns: ____________________________________________

|

|	___________________________________________________________

|

Purchased from: ___________________________________________

|

|	___________________________________________________________

|

___________________________________________________________

|

|	Date Purchased: ___________________

Customer Support

If you need to contact customer support, please call MicroGate at (512)345-7796 weekdays between the hours of 8:00 A.M. and 5:00 P.M. CST, except holidays.

Support may also be obtained by email, support@microgate.com.


Getting Started

Overview

The SyncLink WAN adapter is a high speed synchronous PPP port for computers running Windows. This port connects to remote devices, such as routers or other computers, over a variety of wide area networking media including DDS, ISDN and T1/E1. The SyncLink adapter emulates an Ethernet LAN adapter so applications can communicate over a wide area network as if locally connected.

Planning

Before installing and configuring the SyncLink adapter, gather the following information:

Physical Media Type and Data Rate

The physical media provides the connection between the Windows computer and the remote peer. This connection is usually supplied by a network provider such as the phone company. Examples are DDS 56K, ISDN, T1/E1, FT1 and analog phone lines. Identify and record the data rate of the physical media for future reference.

DCE and Serial Port Type

Each media type has a device that converts the signals of the media to a standard serial port. This device is called the data circuit terminating equipment (DCE). Examples of DCEs are CSU/DSUs, ISDN terminal adapters, and analog modems. The DCE connects to the physical media through a media dependent cable, and connects to the SyncLink adapter through a serial cable. Determine the type of serial interface the DCE requires: RS-232, V.35, or RS-530.

Serial Encoding

Determine the serial encoding used by the remote peer: NRZ or NRZI. PPP communications usually use NRZ encoding.

Network Protocols and Addresses

Determine the network protocols (IP or IPX) used for the connection. For IP communications you need to know the IP address and netmask. IPX requires a network number and Ethernet packet type (Raw, 802.2, SNAP, Ethernet II).

Install the SyncLink Adapter

SyncLink ISA Adapter

Select the adapter base I/O address, interrupt level and DMA channel. The selected resources must not be used by other adapters or devices in the computer. Configure the adapter DIP switches and jumpers to use the selected resources. Write the selected resources down for future reference.

SyncLink PCI Adapter

Resources are automatically configured and do not require jumper and switch settings.

Configure the SyncLink serial interface to match the DCE requirements: RS-232, V.35, or RS-530.

Turn off the computer and remove the computer’s cover. Install the SyncLink ISA adapter in an ISA or EISA slot. Install the SyncLink PCI adapter in a PCI slot. Replace the cover. Connect the SyncLink adapter to the DCE using a serial cable. For RS-232 and RS-530, use a 25-pin straight through data cable will ALL 25 conductors. V.35 requires a special DB-25 to 34 pin Block connector cable available from MicroGate. Connect the DCE to the physical media.

Turn on the DCE and computer.

Install and Configure the Software

The SyncLink WAN PCI adapter is automatically detected when Windows starts.

The SyncLink WAN ISA adapter software must be manually installed using New Hardware in the Control Panel.

After the software is copied to the hard drive, the adapter properties window is displayed. There are three pages of settings that must be configured:

Advanced Settings

Security Settings

Network Settings

The ISA adapter requires manual configuration of adapter resources on the Resources page.

The PPP connection can be enabled or disabled using the MGWAN.EXE program. Start this program from a command prompt by typing MGWAN. This program also provides status information and the ability to trace software events and data exchanges.


Setting the IP Address

This section describes the procedure for assigning the IP address and netmask for the SyncLink WAN adapter. This procedure is the same for all network adapters. The SyncLink WAN adapter requires the IP address to be set manually. Automatic IP address assignment using DHCP is NOT supported.

NOTE: The IP settings are automatically displays after installing the SyncLink WAN adapter during the rebind process.

Open the My Computer window.

Open the Network Connections window.

Right click on the SyncLink WAN network connection.

Select Internet Protocol TCP/IP in the network components list.

Click Properties button.

Select the Specify an IP address radio button.

Enter the IP address and subnet mask.

Click OK.


IPX Settings
IPX Network Number and Packet Type

This section describes the procedure for setting the IPX network number and packet type for the SyncLink WAN Adapter. This procedure is the same for all network adapters. The SyncLink WAN adapter REQUIRES that the network number and packet type are manually selected. The Auto Detect Packet Type option MUST NOT be used.

NOTE: The SyncLink WAN adapter installation must be complete and bindings recalculated before setting the IPX parameters for the adapter.

Open the My Computer window.

Open the Network Connections window.

Right click on the SyncLink WAN network connection.

Select NwLink IPX/SPX/Netbios Compatible Protocol in the network components list.

Click the Properties button.

Select the Manual Frame Type Detection radio button.

Click the Add button.

Select the Frame Type and Network number.

Click OK to accept settings.

Click OK to close IPX properties.


Finding a Network Connection

The Network Connections window contains an icon for each installed network connection. By default, Windows assigns the name ‘Local Area Connection (x)’ where x is the connection number. Select a connection by left clicking the connection icon. The device used by the selected connection is displayed in the left size of the Network Connections window. This information can be used to determine which network connection is the SyncLink WAN adapter.


Troubleshooting

The following  sections describe tools and procedures for verifying the correct operation of your SyncLink adapter and network.

Internet Protocol Ping

Windows includes the PING.EXE program for testing IP networks. This program exchanges IP packets with a specified destination. Use the ping program to test the connection to each computer or router in the path to the destination. See the Windows online help for details about PING.EXE.

Run PING.EXE from the command prompt as shown below:

C:>ping XXX.XXX.XXX.XXX

Where XXX.XXX.XXX.XXX is an IP address such as 200.32.45.7.

If successful, PING.EXE displays the following:

Reply from 200.32.45.7: bytes=32 time 105ms TTL=128

Reply from 200.32.45.7: bytes=32 time 110ms TTL=128

Reply from 200.32.45.7: bytes=32 time 95ms TTL=128

Reply from 200.32.45.7: bytes=32 time 106ms TTL=128

If an error occurs, PING.EXE displays an error specifying a timeout or that the destination cannot be reached.

The following steps verify the network path between computer A and computer R shown in the network diagram.

Ping the LAN adapter in the server.

This verifies the path from computer A to the server.

C:>ping 200.76.23.3

Reply from 200.76.23.3: bytes=32 time <10ms TTL=128

Reply from 200.76.23.3: bytes=32 time <10ms TTL=128

Reply from 200.76.23.3: bytes=32 time <10ms TTL=128

Reply from 200.76.23.3: bytes=32 time <10ms TTL=128

If this fails:

The server may be down, misconfigured or malfunctioning.

The LAN media may be disconnected or damaged.

Ping the SyncLink adapter in the server.

This verifies that the server is forwarding packets and that the SyncLink adapter is installed and functioning.

C:>ping 207.12.32.1

Reply from 207.12.32.1: bytes=32 time <10ms TTL=128

Reply from 207.12.32.1: bytes=32 time <10ms TTL=128

Reply from 207.12.32.1: bytes=32 time <10ms TTL=128

Reply from 207.12.32.1: bytes=32 time <10ms TTL=128

If this fails:

IP forwarding on the server may be disabled.

The SyncLink adapter may be misconfigured or malfunctioning.

Ping the Router WAN port.

This verifies that the SyncLink adapter, the WAN link, and the router WAN port are operating correctly.

C:>ping 207.12.32.2

Reply from 207.12.32.2: bytes=32 time 35ms TTL=128

Reply from 207.12.32.2: bytes=32 time 30ms TTL=128

Reply from 207.12.32.2: bytes=32 time 32ms TTL=128

Reply from 207.12.32.2: bytes=32 time 30ms TTL=128

If this fails:

The SyncLink adapter may be misconfigured.

The CSU/DSU cables may be disconnected or loose.

The serial interface selections for the SyncLink and CSU/DSUs may not be correct.

The CSU/DSUs may be misconfigured or malfunctioning.

The WAN media may be misconfigured or malfunctioning.

The router WAN port may be misconfigured or malfunctioning.

Ping the remote computer.

This complete the verification of the network path between computer A and computer R.

C:>ping 24.76.33.12

Reply from 24.76.33.12: bytes=32 time 165ms TTL=128

Reply from 24.76.33.12: bytes=32 time 185ms TTL=128

Reply from 24.76.33.12: bytes=32 time 200ms TTL=128

Reply from 24.76.33.12: bytes=32 time 165ms TTL=128

If this fails:

The remote station may be down, misconfigured, or malfunctioning.

A router in the network path is down, misconfigured or malfunctioning.

Event Log

To help resolve problems with the SyncLink WAN adapter, view the entries in the system event log with the event viewer program.

Click the Start button on the task bar.

Select the Programs submenu.

Select the Administrative Tools submenu.

Select the Event Viewer menu item.

Once the Event Viewer program is running, select the System log from the Log menu. Look for any entries with a Source of MGWAN. Double click on an entry to view the event details. The following is a list of events for the SyncLink WAN adapter and a suggested course of action. Each event description identifies the adapter generating the event with the text MGWANn, where n is the adapter number.

Event Code:90

An error has been detected for PPP device MGWANn.

The local (incoming) authentication failed.

Action: Check that the configuration for the local authentication protocol, username, and password match that of the remote peer.

Event Code:91

An error has been detected for PPP device MGWANn.

The remote (outgoing) authentication failed.

Action: Check that the configuration for the remote authentication protocol, username, and password match that of the remote peer.

Event Code:92

An error has been detected for PPP device MGWANn.

The DCE or physical media appears to be in loopback mode.

Action: Verify that the local DCE, the remote DCE, and the physical media are not configured for loopback mode.

Event Code:93

An error has been detected for PPP device MGWANn.

The remote peer does not support the IPCP protocol.

Action: Configure the remote peer to allow the IPCP protocol.

Event Code:94

An error has been detected for PPP device MGWANn.

The local IP address could not be negotiated on the PPP link.

Action: Configure the remote peer to allow the SyncLink adapter to specify the local (SyncLink) IP address.

Event Code:95

An error has been detected for PPP device MGWANn

The local IP address conflicts with the remote

IP address. Change the remote or local IP address.

Action: Change the remote or local IP address.

Event Code:112

PPP Device MGWANn.

The link was disconnected due to remote request.

Action: If the disconnect is unexpected, verify that the remote peer does not have an inactivity timeout.

Event Code:113

PPP Device MGWANn.

The link was disconnected due to local request.

Action: The local computer initiated the disconnect due to user request or an error during link establishment. This event should be accompanied by another event describing the reason for requesting the disconnect.

Event Code:114

PPP Device MGWANn.

The link was disconnected due to DCD loss.

Action: Carrier was lost without a remote request for disconnect. Either the remote peer terminated the connection or the physical media encountered an error. Verify that the remote peer does not have an inactivity timeout and that the physical media is operating correctly.

Event Code:115

PPP Device MGWANn.

The link was connected.

Action: No action is necessary.

Event Code:116

PPP Device MGWANn.

The link was disconnected due to LCP negotiation failure.

Action: A required LCP parameter could not be negotiated. Review the settings on the remote peer for the Maximum Receive Unit (MRU) size. The SyncLink requires the remote to support an MRU of at least 1500 bytes. Verify that the remote and local authentication protocols configured for the SyncLink adapter match the remote peer’s configuration.

Event Code:128

PPP Device MGWANn.

The remote peer does not support the PAP protocol.

Action: The remote peer rejected a PAP packet sent by the SyncLink adapter. Verify that the remote peer is configured to use PAP.

Event Code:129

PPP Device MGWANn.

The remote peer does not support the CHAP protocol.

Action: The remote peer rejected a CHAP packet sent by the SyncLink adapter. Verify that the remote peer is configured to use CHAP.

Event Code:144

An error has been detected for device MGWANn.

The remote peer does not support the IPXCP protocol.

Action: The remote peer rejected an IPXCP packet sent by the SyncLink adapter. Verify that the remote peer is configured to use IPX..

Event Code:145

An error has been detected for device MGWANn.

The IPX network number could not be negotiated on the PPP link.

Action: Verify that the SyncLink adapter has been manually assigned an IPX network number and packet type. Verify that this network number matches the network number configured for the remote peer.

Event Code:146

An error has been detected for device MGWANn

The local IPX node number could not be negotiated on the PPP link.

Check for a conflict between the remote and local IPX node numbers.

Verify that remote allows requested IPX node numbers.

Action: Verify that the SyncLink adapter local IPX node number is different than the remote IPX node number. Verify that the remote peer is configured to allow the SyncLink to request a specific IPX node number.

Event Code:160

The user has enabled PPP device MGWANn.

Action: No action is necessary.

Event Code:161

The user has disabled PPP device MGWANn.

Action: No action is necessary.

SyncLink WAN Monitor

The SyncLink WAN Monitor program (MGWAN.EXE) controls and monitors the WAN link.

To start the monitor program:

Click the Start button on the task bar.

Select the Programs submenu.

Select the SyncLink WAN submenu.

Select the SyncLink WAN Monitor item.

Detailed information about the monitor program is available from the help menu.

The left side of the monitor window contains a tree control that contains an item for each SyncLink adapter. Each adapter item has 3 child items, one for each PPP protocol. Each item has an animated virtual LED that changes color depending on the item status. Selecting an item displays the status for that item on the right side of the monitor window. The top of the monitor window contains animated LEDs that indicate the state of the serial signals for the currently selected adapter.

When the connection is active, the adapter status should show:

PPP Phase should be Network

LCP state should be Opened

IPCP state should be Opened if IP is enabled

IPXCP state should be Opened if IPX is enabled

The animated LEDs in the left side of the window should be green.

The Rx OK and Tx OK counters on the right side of the window should be non-zero and should periodically increase.

The animated LEDs at the top of the window should be RED (active) for DTR, RTS, CTS, and DCD.

The following are common problem symptoms and suggested actions:

DTR and RTS LEDs at top of the window are not red.

The selected interface is not enabled. Select the adapter item and click the Enable Interface button.

DCD LED at the top of the window is not red.

The physical connection is not active or the router port is not active. Check the cabling and CSU/DSUs for correct installation. Contact the ISP to verify that the router port is active. Contact the network provider to verify the operation of the physical media (T1 connection).

Only Tx Error counter increases.

The data clocks are not being provided by the CSU/DSU. Check the cabling and CSU/DSU configuration. Check the serial interface selection.

Rx Error increases or Rx OK does not increase.

Check that the serial encoding (NRZ/NRZI) matches that of the ISP router. Verify that the ISP router port is active and transmitting. Check the cabling and serial interface selection.

The adapter and protocol LEDs cycle between yellow and red.

Check the system event log for errors related to authentication and misconfiguration.

Event and Data Tracing

The SyncLink monitor program provides advanced diagnostics capability with the trace feature. The trace feature writes information to a disk file that contains time stamped events and data in ASCII text form. Interpreting the trace file requires a thorough understanding of the PPP protocol. In most cases trace files are created at the request of MicroGate support personnel. View the monitor program online help for instructions on using the trace feature.


Using SyncLink with Cisco Routers
Using the SyncLink WAN Adapter with Cisco Routers

The SyncLink WAN adapter uses synchronous serial communications for PPP connections. Use the following commands to configure a CISCO router serial port for synchronous PPP. These commands can be issued from the configuration console or by a telnet session to the router. Other brands of routers should have similar settings. Consult your router documentation for more details.

1. Select the serial interface to configure.

(config)# interface serial 1

2. Select PPP encapsulation on serial interface.

(config-if)# encapsulation ppp

3. Select NRZ or NRZI encoding.

For NRZ use:

(config-if)# no nrzi-encoding

For NRZI use:

(config-if)# nrzi-encoding

4. Select synchronous HDLC.

(config-if)# physical-layer sync

Additional configuration commands are necessary for selecting authentication options. The settings are application dependent. Refer to the Cisco documentation for more details.